Repository navigation
ci: sync fork and wait for remake in OSC prod on release - #25
Merged
Merged
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
.github/workflows/sync-fork-prod.yml: when a GitHub release is published (or manually viaworkflow_dispatch), trigger a sync-fork of this upstream repo in OSC prod (maker.svc.prod.osaas.io, served from Elastx) and wait for the remake to finish. Same flow and safeguards as the dev workflow (records the order id before the sync, requires it to change, fails onFAILED/ERROR/missing order).Required: Actions secret
OSC_PROD_MAKER_API_KEY(prod maker-manager bearer API key). The job fails fast if it is missing.Test plan
workflow_dispatch, confirm green after the prod remake completesLessons
Releases created with the default
GITHUB_TOKENdo not triggerreleaseworkflows; the release must be published by a user or a PAT. This changes prod, so the first run should be a deliberate manual dispatch.🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com